Release Notes

Here you will find release notes for the most recent versions of EMu. Details include:

Technical requirements
New Features
Improvements
Issues Resolved

EMu 6.3

Release Date: 07 August 2020

Requirements

For Windows 10, Windows 8.1, Windows 8, Windows 7
Texpress 9.0.01 or later
TexAPI 6.0.012 or later
Perl 5.8.8 or later (excluding 5.10.0)

New Features

Integrated Pest Management (IPM) improvements

In response to a collaborative request from EMu IPM users including staff from the Smithsonian National Museum of Natural History and the Natural History Museum, London the functionality of the Trap Events module has been extended to allow capturing additional data relating to pest issues associated with museum collections. Changes include:

Renaming the Trap Events module to Pest Events to better reflect the extended role of the module.

Two new record types (giving a total of three):

Type	Details
Trap	The original Trap Events record type for recording details of what was found in a trap on a given date. Some changes have been made to labels and field layout for consistency with the two new record types.
Visual Inspection	A new record type intended for recording planned environment or specimen inspections.
Incident	A new record type intended for recording casual pest sightings. A casual pest sighting is one that occurs outside of a planned Visual Inspection.

A new Objects tab to record objects or specimens involved in an infestation. The Catalogue module now includes a reverse attachment tab that displays pest events associated with an object / specimen.
A new Actions tab to record any immediate and long term measures taken to resolve a reported pest presence or issue.

EMu 6.1

Release Date: 20 December 2019

Requirements

For Windows 10, Windows 8.1, Windows 8, Windows 7
Texpress 9.0.01 or later
TexAPI 6.0.012 or later
Perl 5.8.8 or later (excluding 5.10.0)

New Features

Condition Update, Re-identification, Relocation & Revaluation Privileges

Operations Registry entry privileges have been added for the Condition Update, Re-identification, Relocation and Revaluation tools. Previously, access to these tools required that users were given the Global Replace (daReplace) Operations privilege. While users with the daReplace privilege will still be able to use these tools, it is now possible to give users access to each of these tools without also providing them with the Global Replace privilege.

The new privilege values are:

Tool Name	Privilege
Condition Update	`daRecondition`
Re-identification	`daReidentify`
Relocation	`daRelocate`
Revaluation	`daRevalue`

Details here.

Other New Features & Improvements

Feature / Improvement	Details
Improved Contact Sheet thumbnail drawing	This improvement reduces the time taken to draw Contact Sheet thumbnails and was implemented to address a long-standing but intermittent issue that could cause the Contact Sheet to be cleared and redrawn multiple times during the display of the Contact Sheet.
Added persistent Registry entries	Changes to the EMu upgrade procedures mean that EMu Registry entries are no longer reset during an upgrade. This prevents user modified Registry entries (e.g. for Reports) from being reset and allows the possibility to add custom fields to the Registry module (e.g. notes), the values of which would persist between upgrades.
Added support for 64-bit Microsoft Office Reports	Support has been added for running reports generated using 64-bit Microsoft Office applications (e.g. Excel). This feature requires that Microsoft Office System Drivers (Microsoft Access Database Engine 2010 Redistributable) are installed.
Improved multimedia file processing for specific file formats	The processing of multimedia files containing multiple images (e.g. PDF or TIF files) has been improved. This change significantly improves the time taken to generate image resolutions for large multi-page PDF files. For example, when generating an image resolution of a multimedia file that contains multiple images, only the first image is loaded and used if the destination format does not support multiple images. Prior to this change all images were loaded but only the first was used. If the destination format does support multiple images, all images are loaded and used for the image resolution.
Added No Date Circa Date field support	The abbreviation `n.d.` for No Date can now be used in text date fields with associated earliest and latest date fields. In this case, no values are inserted in the associated date fields.
Added support for Group-specific Command Centre favouites	Support has been added to allow the use of different Command Centre favourite modules for each of a user's login groups.
Added Open dialogue when editing HTML in an external application	Changes to Microsoft Windows (particularly in Windows 10) have made it difficult to specify the application to be used for editing a particular file type. To make this easier a dialogue has been added to allow users to specify the application to launch when editing HTML files in an external editor.
Added Loans module Open Loan Status check box	A check box has been added to the Loans module, Information 1 search tab Loan Status group to allow searching for open loans.
Changed Ribbon state behaviour	The module window Ribbon state (e.g. the items contained in, or the position of, the Quick Access Toolbar) is now persisted in the EMu Registry instead of a user's roaming Windows profile. This resolves inconsistencies that could occur when a user changes the computer they use to access EMu. In addition, Ribbon state is now loaded when a module receives focus and persisted when the module loses focus. This means that when two modules of the same type are open, changes to the Ribbon state of the first module will be reflected in the second module when focus changes from one to the other.
Increased Multimedia metadata field sizes	The size of the Multimedia module fields used to display metadata information on the EXIF, IPTC and XMP tabs has been increased to make use of the increased module window size.
Changed Command Centre resize behaviour	The Command Centre no longer resizes automatically to shrink when it is moved below the bottom of the screen and expand again when moved back up. This change removes behaviour that functioned poorly especially when the Command Centre was expanding again and makes the behaviour of EMu windows consistent and predictable.
Added Condition module Multimedia tabs	The standard Multimedia tabs have been added to the Condition module.
Added Command Centre Remove from Favouites menu option	A menu option has been added to remove a favourite module when right-clicking its corresponding button in the Modules section of the Command Centre.
Changed pop-up Field Level Help style	Some minimal styling changes have been made to the Field Level Help pop-up window to match the main EMu module styling introduced in EMu 6.0.
Changed button style	The colour of buttons has been changed from white to grey so they can be more easily identified and visually distinguished from their background.
Added support for Archive hierarchy natural sorting	Functionality to allow natural sorting of the Archives hierarchy entries has been added.

Display Scaling Issues Resolved

Corrected scaling of group box headers when the display is scaled.
Implemented resizing the Ribbon toolbar when the display is scaled.
Corrected the blurry EMu title bar icon when the display is scaled.
Fixed an issue where restored module dimensions (e.g. the module height and width when using the Save Last Size Display option) were too large when the dimensions were saved on a scaled display but restored on a display that was not scaled.
Fixed an issue where controls would overlap when resizing a module on a scaled display.
Fixed an issue where the media toolbar buttons were partially obscured on a scaled display.
Fixed an issue where the text for some controls did not scale when moving a module window between monitors with different scaling.
Fixed an issue where the List View row height was incorrect when a module was opened on a scaled display.
Fixed an issue where the Command Centre buttons resized incorrectly when the Command Centre was moved to a scaled display.
Fixed an issue where the Command Centre section headers would did not resize when the Command Centre was moved to a scaled display.
Fixed an issue on a scaled display where clicking the up / down scroll bar buttons of a Link Grid would not always scroll the grid.
Fixed an issue where the Command Centre or module windows saved position would not always be correctly restored when the saved position was on a secondary display in a multiple monitor set-up.

Other Issues Resolved

Fixed an issue where the values of a Lookup List in a hierarchy that includes values from a combo box were not correctly filtered after loading default values.
Using Ditto to populate parent fields no longer allows a circular loop to be created.
Fixed an issue where Insert Defaults containing newline characters did not load correctly Rich Edit fields.
Fixed an issue where the Shortcuts View did not update correctly when Default Values were changed.
Fixed an issue where the Shortcuts View did not refresh correctly after a New Search.
Fixed an issue where the emubatch utility did not stop local loads when the -L parameter was used.
Fixed an issue where generating a multimedia resolution that already existed did not update the resolution details.
Fixed an issue where attachment columns in the Shortcuts View were not updated when a record was attached or a Default Value was loaded to the corresponding field in the module window.
Fixed an issue where the Shortcuts View was not correctly updated when selecting a record in Archive Browse View or Thesaurus Browse View.
Fixed a Grid index out of range error that occurred when a Column Access Modifier Registry entry hid information in List View.
Fixed an intermittent issue when pasting from EMu into Microsoft Excel that resulted in the error Microsoft Excel cannot paste the data.
Fixed an issue where the value of a combo box would disappear after selecting the down key for the first time and then selecting the tab key to exit the control.
Corrected the display of Unicode characters in the Multimedia module, EXIF metadata.
Fixed an issue where the auto fill behaviour of the Taxonomy module Higher Classification tab fields did not function in the same manner when the fields were filled using the Ditto functionality as opposed to when they were manually keyed.
Fixed an issue where the Tabs pane lost focus in the Multimedia module when navigating away from the Multimedia tab using the arrow keys.
Fixed an issue where users with Show Hidden lookup permissions could not save records when hidden lookup table entries are selected.
Correctly disabled all Ditto functionality in the Thesaurus module.
Fixed an issue where Exhibit Objects module Task notifications were not generated.
Fixed an issue where the Disable Also Search character (the percent symbol %) was not included when saving a dynamic search group.
Fixed an error Can’t use arithmetic operator on type INTEGER when removing an IRN from a static group.
Fixed an issue where the Thesaurus module Hierarchy View did not display the correct hierarchy after changing languages.
Fixed an error Unable to resolve “Key12” when a record column containing the pipe character | is used to look up a Registry module value, for example, when looking up column values for the Image Display Registry entry.
Fixed an issue where the Multimedia toolbar buttons might not have been correctly enabled or disabled when moving between records.
Fixed an issue where Link Grid controls with the duQuery Column Access permission but not the dvDisplay permission were shown as read-only in the Display views.
Removed the restriction that prevented some values from being pasted into Search mode fields, e.g. greater-than or less-than characters in a date field.
Fixed an issue where NOT searches involving fields that were specified to also search other fields (i.e. using the Also Search functionality) returned records that did not correctly match the specified search values.
Fixed an issue where deleting the last row from the List View when thumbnails were displayed in the list resulted in the error TexAPI Error: End of file. (Number -18).
Fixed an issue where Security|Update Registry entry values were not applied to Group module records created via the Save Group dialogue.
Fixed an issue where the Thesaurus module View Attachments functionality did not correctly display Thesaurus record attachments.
Fixed an issue in Search mode where values entered into some fields of the Collection Events module Aquatic tab were not included in a subsequent search.
Fixed an issue that resulted in an error like Bad column “SecDepartment_tab” in security profile… when specifying a nested table column in a Security|Update Registry entry.
Fixed an issue where the error message invalid date format would display when selecting a Pop-up Calendar and the date order of the Date Input and Date Output Registry entries differed.
Fixed an issue where read-only Link Grid values could be cleared using the Delete key.
Updated the EMu website URL displayed in notifications.
Fixed an issue where the List View row numbers did not display correctly in right-to-left language display mode.
Fixed an issue where the Multimedia tab Multimedia toolbar Attach button was not correctly enabled the first time multimedia was attached after the module was opened.
Fixed an issue where the audit summary information displayed in the Audit module on the Summary tab did not display all audited changes. All changes were, however, displayed on the Audit tab.
Fixed an issue where Column Access Modifier Registry entries were not correctly applied in Search mode when a value was selected from a Lookup List.
Fixed an issue where the format of XMP metadata copied from a master image to derived images (via the Metadata|Embed Registry entry) was incorrect. This prevented viewing the XMP metadata in some other applications (e.g. Adobe Photoshop).
Fixed an issue where EMu would hang after adding a (non-IRN) thesaurus term to a link grid via the File>Close and Attach menu option.
Fixed an issue where the Ctrl-C shortcut would not copy text in the Field Level Help window.
Limited the amount of memory that can be used for manipulating images using the ImageMagick libraries to 1.6GiB. This reduces the incidence of memory allocation errors when handling large images.
Fixed an issue that prevented pasting all multi-lingual values copied from the Lookup Tables module List View.
Fixed an issue where the Parties module Ribbon did not update correctly after synonym Parties records were added to the matching set.
Fixed an access violation when viewing or updating an attachment when the Save Last Position option is set.
Fixed the position of the tabs area when changing between left-to-right and right-to-left language modes.
Fixed an intermittent issue when selecting a tab in the Tabs pane would not transition to Details View.
Fixed an issue where Status bar text was mirrored in right-to-left language mode.
Reverted the appearance of the selected Sort after Search sort back to being displayed in bold text from being displayed in a different colour (which had been a workaround for an issue with the underlying styling functionality).
Fixed an access violation when viewing or updating an attachment after changing to right-to-left (e.g. Arabic) language prompts.
Fixed an issue where some Ribbon images were not appropriately mirrored in right-to-left language mode.
Fixed an issue where two ampersand characters would be displayed instead of one in the group box caption Hybrid & Parentage on the Taxonomy module Classification tab.
Fixed an access violation when a focused link grid column is hidden by Column Access Registry entry permissions when transitioning between view modes.
Fixed an issue where an error message, for example A component named CatalogueBtn already exists, would display when selecting the Ribbon File (AKA Application) menu.
Fixed an issue where the error message Bad Condition Name ConHandlingInstructions or Bad Valuation Name ValReasonForValuation might display when opening a module.
Fixed an issue where the List View display was muddled in right-to-left language mode when a multimedia thumbnail was included as one of the list columns.
Fixed an issue where a TexAPI syntax error would occur when including the case-sensitive search operator (\=) in the searches of some fields.
Fixed an issue where Tab Switching did not function in Search mode when displaying all languages in a multi-language environment.
Fixed an issue where the Command Centre Help and Exit buttons did not function correctly when added to Favourites.
Fixed an issue where non-ASCII characters entered in an HTML display control (e.g. the Narratives module Narratives tab) would be garbled on record save.
Corrected the Tool Tip Title and Description for the Remove Record Ribbon element from the Selection group.
Fixed an issue when importing where ANSI encoded characters with diacritics would be garbled.
Fixed and issue where a blank tab would display accompanied by the message Cannot focus a disabled or invisible window when using the Find a Field utility when a field that is used for Tab Switching had focus.
Corrected the handling of leap years in the EMu Museum client Catalogue module Condition tab Next Due group Notification Date field.
Fixed an issue where column headers did not display in a number of list dialogues, for example, the Reports and Sort list dialogues.
Fixed an issue where an access violation error would occur or the client would hang in certain circumstances when displaying the Archives tab Archive hierarchy.
Fixed an issue where focus would change to the first field of a tab when saving the record or selecting a value from a field that triggers Tab Switching.
Fixed an issue in the Multimedia module when generating multimedia resolutions for selected records where the Scaled setting was ignored.
Corrected the multimedia file name included when displaying all multimedia in the Multimedia tab image pane.
Fixed an issue when the auto-incrementation facility is not triggered when globally replacing the values of a unique field.
Fixed an issue where the file extension of supplementary multimedia in the Multimedia module was not included in the supplementary file Identifier field.
Fixed an issue where the EMu client would unexpectedly shut down when adding a PDF or PSD file to the Multimedia module and a Convert Registry entry was specified for those document types.
Reverted the Multimedia tab multimedia display to always initially display thumbnails.
Fixed an issue where previous report files located in a user's local report directory were not removed when a subsequent report was run.
Corrected an issue where a field explicitly set to display text in a right-to-left direction in a left-to-right system would only display text left-to-right.
Fixed a resource allocation leak that, after extended application use, resulted in an unexpected shut down with error messages like Canvas does not allow drawing and / or The handle is invalid.
Fixed an issue where the server-side auditing facility could fail with the log message Can’t kill a non-numeric process ID…
Fixed an issue where the server-side auditing facility could fail with the log message Use of uninitialized value $DrainPid…
Fixed an issue where the Editing general option on the Options box Editing tab would revert to the overwrite option if the Editing tab was revisited after the option was changed.
Fixed an issue where the Registry module Module menu item under the Ribbon File menu was empty instead of containing a list of all of a user's open, favourite and accessible modules.
Removed the incorrect requirement for report design (daDesign) privileges to add a new Scheduled Export.
Corrected the display of Unicode in the HTML display control used, for example, on the Narratives module Narratives tab and on the Field Help module Description tab.
Fixed an issue where the error Column operation performed before row has been accessed. (Number -31) would occur when closing the application with an open module in New mode.
Fixed an issue where the application could exit when using the Sites module GEOLocate Save to your application button if the Lat/Long tab had not previously been visited.
Fixed an issue where spell checking would continually replace a Not Found word if that word also appeared in the Replace With word(s).
Fixed an issue where the modified time of report files shown in the Report Properties dialogue could be incorrect by 2 hours.
Fixed an issue where the log files associated with a long-running Scheduled Operation (e.g. an Image Import) were not all added to the Result Files section of the appropriate Operations module record when the operation completed.
Fixed an issue when uploading a modified report file that resulted in the uploaded file being corrupted and as a result the report would not run.
Fixed an issue where the background of the icon displayed in the Reports list view Title column was black on Windows 10.
Fixed an issue where notifications were not sent when EMu server date format used text months (e.g. 25 December 2019 rather than 25/12/2019) and the server data order was not day-month-year (dmy).
Fixed an issue where incorrectly spelled words in Rich Edit controls containing more than one line of text were not highlighted correctly.
Fixed an issue when opening a module with the Save Last Size Display option specified that resulted in the error System Error. Code: 1400. Invalid Window Handle.
Increased the row length available to store audit information.
Fixed an issue where the last character in the Audit module Summary field was not displayed.
Fixed an issue were Rich Edit controls that were restricted to a single line allowed multiple lines to be entered.
Fixed an issue that resulted in the error message “name” attribute is missing when importing reference links.
Fixed an issue in Insert mode the prevented the display of Rich Edit control background colours.
Fixed an issue where the embedded GEOLocate client would not display correctly when Internet Explorer options are limited to the local machine via the Windows Security_HKLM_only registry entry.
Fixed an issue where the contextual Field Tools Ribbon tab would not display for read-only fields even when the View Attached commands were available.
Fixed an issue when attached objects removed from an Exhibit Event record that didn’t have a corresponding Exhibit Objects record resulted in the error TexAPI Error: Internal Error: evdelete: Bad Delete tree. (Number -1) at offset 0 when the record was saved.
Suppressed the logging of unnecessary Bad sort order value messages by the server-side emulutsrebuild utility.
Fixed an issue that prevented pasting values into Link Grids controls.
Fixed an issue that caused warning messages about uninitialised values to be included in the output of the server-side emunotify utility.
Fixed an issue where Rich Edit controls associated with a Link Grid control did not display the correct data when the Rich Edit was first shown.
Fixed an issue where an Argument out of Range error could occur when viewing Catalogue records where Tab Switching was based on the object type, the object type was an archive and the Archive tab was visible.
Fixed an issue that prevented the generation of Locations module summary data in multi-lingual environments.
Fixed an issue that caused unnecessary duplicated rows in double nested tables when using the Merge Records Scheduled Operations type.
Fixed an issue that resulted in an error being reported when running the Multimedia module PowerPoint Image reports when reporting on non-image multimedia.
Fixed an issue where values entered into an empty HTML display control (e.g. on the Narratives module Narratives tab) were lost if the tab containing the display was navigated away from before the record was saved.
Fixed an issue where an erroneous value could be inserted into the focused grid row after sorting a column of the grid and that column was associated with a Lookup table.
Fixed an issue that resulted in an error when setting Format Registry entries for client-only columns.
Fixed an issue where attempting to use the scroll bar of the module window Field Level Help resulted in the field level help text being cleared.
Fixed an issue where ADO reports including multimedia with an apostrophe in their file name did not display correctly.
Fixed an issue where clicking on a Tree View node expand / collapse button did not cause the node to expand or collapse on a scaled display.
Fixed an issue where the circa date functionality could be invoked even when circa identifiers were not specified.
Fixed an issue where the highlighting of misspelt words was incorrect in Rich Edit fields containing multiple lines of text.
Fixed an intermittent access violation error when the loading of a large Lookup List was cancelled.
Fixed an issue where the Thesaurus Browse View did not display the current record when the Always show record setting was active and automatic sorting of search results occurs.
Fixed an issue where the visibility of the Thesaurus and Archives Browse Views was not retained between EMu sessions.
Fixed an issue where the Command Centre could not be fully resized after adding Favourite modules.
Fixed an issue where a blank area displays at the bottom of the Command Centre window after removing a favourite module when the Modules section is collapsed.
Fixed an issue where the Command Centre Favourites section does not display all added modules and does not resize correctly when expanded after adding modules when the Favourites section is collapsed.
Fixed an issue where a blank area displays at the bottom of the Command Centre window after resizing the window when the Modules section is collapsed.
Fixed an issue where Command Centre hints were not translated after changing the prompt language.
Fixed an issue in the Command Centre where dragging and dropping a module onto the Favourites section does not add the dragged module to Favourites when the Favourites section is empty.
Fixed an issue where users other than the owner added to the Security access permissions of a group were not saved.
Fixed an access violation error that would occur when closing a module window while a grid context menu was being displayed.
Fixed an access violation error when deleting a row from a Link Grid that contains non-visible columns.

EMu 5.0

Release Date: 16 November 2015

Requirements

Windows 2003, Vista, Windows 7, Windows 8, Windows 8.1, Windows 10
Texpress 9.0.001 or later
TexAPI 6.0.012 or later
Perl 5.8.8 or later

New Features

Reporting Formats

EMu's Reporting subsystem was modified in order to bypass some filtering which occurs when a Crystal Report or Microsoft report (Excel, Word, etc.) is generated out of EMu. Bypassing the filtering improves report generation and performance. It is now possible to report directly to an Open Database Connectivity (ODBC) data source or to an ActiveX Data Objects (ADO) Recordset object.

The Reporting subsystem was modified in two major ways:

Crystal Reports.
In order to build and generate a report, Crystal Reports requires a .csv file with the exported EMu data. In previous versions of EMu, data was exported as XML and then filtered to produce one or more ODBC compliant .csv files. The filtering process has been bypassed and EMu is now able to generate the ODBC data source directly.
Note: This change does not affect the way that you build a Crystal Report, it simply means that the ODBC data source (one or more .CSV files) output by EMu is generated far more efficiently. With the Reports|Type Registry entry it is possible to specify whether the filtering process is bypassed or not.
Two new report formats have been introduced that report directly to an ActiveX Data Objects (ADO) RecordSet object (XML) rather than reporting to an ODBC data source (CSV). The new report options are:
- Crystal ADO: report using ADO RecordSets for Crystal (which are accessible via Crystal's ADO connector).
- Microsoft ADO: report using ADO RecordSets for Microsoft products.

Existing Crystal Report and Microsoft (Excel, Power Point and Word) report types that currently connect to an ODBC data source can be changed to use an ADO Recordset.

See the Reports section of this Help for a description of ADO reporting.

Tip: A PDF is also available with a complete description of ADO reporting.

Improvements

Performance Improvements

Performance improvements have been made to sorting, exact matching, reporting and attachment searches in EMu. Some examples of the observed performances improvements are:

Sorting improvements:

Module Records	Records	Old Time	New Time	Factor Improvement
Catalogue	270,000	2:15	0:45	x3
Parties	25,000	1:20	0:02	x40
Events	22,000	2:15	0.015	x90

The performance improvement increases with the size of the module. The modules are listed from small to large.

Exact matching improvements:

Module Records	Records	Old Time	New Time	Factor Improvement
Catalogue	250,000	1:30	0:15	x6
Thesaurus	115,000	6:45	0:15	x27
Events	22,000	2:20	0.01	x80

The performance improvement increases with the size of the module. The modules are listed from small to large.

Reporting improvements:

Module Records	Records	Old Time	New Time	Factor Improvement
Bibliography	6,500	1:00	0:10	x6
Parties	70,000	10:00	1:00	x10

The performance improvement increases with the size of the module. The modules are listed from small to large.

Attachment searching improvements:

Module Records	Records	Old Time	New Time	Factor Improvement
Sites	10,000	10:00	1:50	x6
Parties	200,000	60:00	9:30	x11

Issues Resolved

Fixed an issue when using the Import Tool where a new line character in appended data assigns the data to the incorrect row of the specified column.
Fixed an issue when using the Internal tab of the Movements module to update the Location of an attached object; the irn of the new Location would be put in the Movement Notes of the Catalogue instead of the Movements Notes of the Movements module.
Corrected the display of the full name of the Source in Accession Lots module Summary Data.
Changed the behaviour when adding image types that support multiple images in a single file (specifically the TIFF, TIFF/EP and DNG file formats) to the Multimedia module. Previously the "last" image from the file was selected as the Multimedia module master image; now the "first" image is used.
Fixed an issue where a mini-multimedia component linked to a grid did not update when the grid row was changed.
Fixed an issue where dates before 30 December 1899 entered in a control via the pop-up calendar were off by one day.
Fixed an issue where the value of the active cell of a grid control was retained when moving between records.
Fixed an issue where controls would appear outside of the tab boundaries when the View>Thumbnail menu option was specified.
Fixed an issue where updating Holder records in the Locations module did not trigger updates to the associated fields of Catalogue records using that location.
Fixed an issue where the Operations module could not be accessed with the error "You are not a registered user of "eoperations" table."
Fixed an issue where Lookup List buttons were not correctly enabled or disabled when a record was set to read-only using Record Level Security.
Fixed an issue where IMu server log files would overlap when the IMu server configuration setting process-count was greater than one.
Corrected the placement of the French translation for the "Time Moved" caption in the Tools>Relocate dialogue.
Fixed an issue where aborting an operation (e.g. reporting) would cause the display of a different record than the record that was displayed prior to the operation.
Fixed the display of Unicode characters in Admin Task controls.
Fixed an issue where the Lookup List values displayed might not be correct for Lookup hierarchies where the hierarchy included grid and edit controls and those controls were linked to another grid control.
Fixed an issue where merging records via the Additional Search>Merge menu option would produce the error "TexAPI Error: (Number 0)".
Fixed an issue where generating resolutions of a TIFF file and a Multimedia|Metadata|Embed Registry entry specified that some or all of the tags should be embedded in the generated resolution resulted in an "Access Violation" error.
Fixed an issue where the emuoperations utility did not correctly handle date orders other than "dmy" (day, month, year).
Fixed an issue where Lookup List hierarchy values associated with a grid were not automatically back-filled if the Lookup button was used and the cursor was not in the grid.
Fixed an issue while running multiple simultaneous multimedia imports in multiple instances of the EMu client where the system-generated multimedia resolutions could be assigned to the wrong multimedia record.
Fixed an issue where data might not have been saved when adding a Lookup value to an edit field that is part of a Lookup hierarchy with a grid field and both fields are linked to another grid field.
Fixed an issue where data might not be saved to the correct row when the user invokes undo (e.g. via the Edit>Undo menu option) when the cursor is within a grid that is linked to another grid.
Added a missing entry to the crontab configuration file used for new EMu installations.
Fixed an issue where Lookup Lists did not sort according to the user-defined Sort Order in the Lookup Lists module.
Fixed an issue where the incorrect start and end dates values were set when a user-initiated export was run via the Tools>Exports... menu dialogue.

EMu 4.3

Release Date: 07 August 2014

Requirements

Windows 2003, Vista, Windows 7, Windows 8, Windows 8.1
Texpress 8.3.013 or later
TexAPI 6.0.011 or later
Perl 5.8.8 or later

New Features

Issues Resolved

Issue	Resolution
The output file for XSLT based reports is saved in files with a `.html` extension. If the output type specified in the report via <xsl:output> is not HTML, then the file extension should reflect the output type specified.	The extension of the file created for an XSLT based report is based on the type specified in the `<xsl:output>` tag.
The label name of the multimedia thumbnail in List View in the Multimedia module is shown as MulDocumentType. The title is displayed regardless of the display language selected. The label should be changed to Multimedia Thumbnail for English and an appropriate translation for other languages.	The label has been changed from MulDocumentType to Multimedia Thumbnail. Translations have been added for other languages.
The Summary Data and Extended Data calculations for the Collections Description module do not handle multiple languages correctly. The data generated is correct where a single language system is used.	The Summary Data and Extended Data calculations for the Collections Description module now handles multiple languages correctly.
The Global Replace facility does not allow a global edit to be performed on a hierarchy where the level being changed is read-only. The limitation ensures that only existing hierarchy combinations may be used in a replacement. The restriction means that global replacements cannot be used to change a read-only hierarchy to a different existing combination. Ideally it should be possible to alter the value in a hierarchy where the level being changed is read-only.	The value in a hierarchy where the level being changed is read-only can now be changed. If the value would form a new hierarchy combination, then the Global Replace is still allowed. The new hierarchy will be added to the Lookup List.
An invalid server-side schema file may be produced if a field's prompt has a single quote character in it. The field prompt is defined in the database rather than the prompt displayed in the Windows Client. A correct schema file should be generated even if a field's prompt contains a single quote.	A valid schema file is now generated even if a field's prompt contains a single quote character.
The Windows client installer program does not include the version information in the Add/Remove Programs section of the Windows Control Panel. Some desktop roll-out software uses the version information to determine which software packages need to be upgraded on a given computer. The version number should be in the same format as that used with EMu releases.	Version information is now added to the EMu entry in the Add/Remove Programs section of the Windows Control Panel.
The Windows client creates missing ODBC Data Sources for each module when it is invoked. If an ODBC Data Source is damaged, that is key entries are missing, the entry is not repaired. A check for damaged entries which can then be repaired should be performed.	Damaged ODBC Data Source entries are now repaired when the Windows client is invoked.
When the selected row in a LinkGrid control with RichEdit controls associated with it changes, the cursor position in the associated RichEdit control is not reset to the beginning of the field. The cursor should be placed at the start of the field when the row in the grid changes.	The cursor in a RichEdit control associated with a LinkGrid is now placed at the beginning of the field when the selected row in the grid changes.
The Lookup List server (lutserver) is used to maintain the values in Lookup Lists. When a hierarchy that contains multiple values at each level is checked, the server may be slow to check that each combination exists as a Lookup combination.	The time taken to check hierarchies containing multiple values at each level has been improved significantly.
The server-side Registry manipulation programs (emuregload, emuregdelete and emuregupdate) do not correctly handle Registry entries over 8192 characters long. The error messages emitted may be somewhat cryptic.	The Registry manipulation programs have been enhanced to handle infinite length Registry entries. Better error messages are displayed and a new program `emuregcheck` has been added to allow the format of existing Registry entries to be checked.
Server-side scripts that are executed on behalf of a user should produce output in the language the user last used in the Windows client. A new Registry entry specifying a user's prompt language should be added. The entry can then be checked by scripts and used to produce output in the correct language.	A new Registry entry containing the language last used by a user has been added. The entry is updated automatically by the Windows client and is used by server-side scripts to produce output in the correct language.
The `System\|Client\|Version` Registry entry does not allow the release date to be included as part of the minimum supported version number. For example, an entry of `4.2` allows all version 4.2 clients to be invoked. In some instances a finer grain of control is required. For example a value of `4.2 (1404031)` would block all clients before version 4.2 (1404031).	The `System\|Client\|Version` Registry entry has been changed to System\|Setting\|Client\|Version and support for release dates has been added.
If the Calendar pop-up is used to select a date for performing a query, the value placed in the field is not wrapped in double quotes. If the date format is set to `dd MMM yyyy`, the search generated will treat the date as three separate components rather than a single date value.	When a date is selected from a Calendar pop-up that is to be used in a search, the date is now enclosed in double quotes, ensuring a single date value is used.
The Narratives module and other modules containing HTML based editing may not change to Edit mode when the HTML version of the data is modified. The issue only arises where Internet Explorer 11 is installed on the user's computer.	When HTML based data is modified, the module is now placed into Edit mode for computers with Internet Explorer 11 installed.
Export records created via the Scheduled Exports facility cannot be deleted. The Export records were meant to provide a complete audit of all data exported and so cannot be deleted. However, due to space considerations, deletion of older Export records would be useful.	Export records may now be deleted.
The `fifoserver` does not output Unicode (UTF-8) characters correctly when logging calls and outputting results. Non-Unicode based systems (e.g. Latin 1) are not affected.	The correct Unicode characters are now output by the `fifoserver`.
The title displayed below thumbnails in Contact Sheet mode may be incorrect if the order of the matching records has been modified in List mode. The issue is caused by the Contact Sheet cache not being cleared when records are re-ordered.	The correct title is now displayed below thumbnails in Contact Sheet mode when records have been re-ordered.
The server-side Lookup List rebuild program `emulutsrebuild` generates an error on Unicode based systems when a Lookup List value is not encoded correctly. Since the data is already in the system, albeit incorrectly, emulutsrebuild should generate a warning and continue processing data.	`emulutsrebuild` now generates a warning and continues processing data if an invalid Unicode sequence is encountered.
The error message Column "irn_1" is read only - primary key. in Column irn may be displayed after a number of modifications have been made to existing records. The message does not appear when creating new records. The appearance of the error message is somewhat random.	The error message is no longer displayed when changing existing records.
The list of values in a given Lookup List may not be correct when the field is part of a hierarchy containing a double nested grid. A double nested grid is a LinkGrid control that is associated with another LinkGrid control. Selecting a row in an associated grid alters the contents of the LinkGrid control. The values displayed are generally a sub-set of the allowable values.	The list of values displayed for a Lookup List in a double nested grid is now the complete set of values.
Audit records created with ISO-8859-1 (Latin 1) characters as part of the data may not display correctly in the Audit Trails module. The Latin 1 characters are converted to Unicode (UTF-8) characters and stored in the Audit table. The conversion should not occur.	Audit records containing Latin 1 characters are now stored and displayed correctly in the Audit Trails module.
The Microsoft Visual Basic error message Run-time error '1004': This operation cannot be done because the data is refreshing in the background. may be displayed when running the Data Dictionary report in the Field Help module. The error may also occur when other Microsoft Excel based reports are invoked.	The error message is no longer displayed when the Data Dictionary report in the Field Help module is run.
The email notifications generated nightly by the server-side `emunotify` script may not be sent if the data in the email notification contains a closing bracket ')' at the end of a line.	The email notifications are now generated and posted regardless of the data in the notification message.
The error message Invalid selection has been made. Please use the Lookup List may appear when a new insertion is commenced. The error only occurs if the module has a read-only hierarchy of Combo Boxes and one of the Combo Boxes has the AllowEmpty property set to `false`.	The error message is no longer displayed when a new insertion is commenced.
The Quality field in the Image Attributes group on the Resolutions tab of the Multimedia module is not populated when the Multimedia>Generate Resolution>Selected Records command is selected from the Menu bar.	The Quality field is now populated when the generate resolutions command is invoked.
If the Edit>Ditto>All Fields command is invoked in the Value (Edit) field in the Registry module, then only the value fields are dittoed. The Value (Edit) field remains empty.	All fields are now dittoed correctly.
If a sort is executed in a LinkGrid control that contains more than two rows, the data in some cells may appear as though it is not sorted. If the screen is repainted (by covering the grid and then uncovering it), the grid is drawn correctly.	The data in the LinkGrid control is now displayed correctly after the data is sorted.
The Audit Record field on the Summary tab in the Audit Trails module does not resize when the form size is increased. The field remains the same size as it was when the module was invoked.	The Audit Record field now resizes correctly when the form size is increased.
If a selection of records is copied from List View and then pasted into Microsoft Outlook, the data does not appear in a formatted table. The data should appear in an HTML based table.	Data copied from List View and pasted into Microsoft Outlook now appears as a formatted table.
If one or more records are copied from List View and the first column of data copied contains empty values, the data in rows where the first column is empty is moved to the left by one column when the records are pasted into Microsoft Outlook or Word.	Rows where the data in the first column is empty are now pasted correctly, that is with an empty first column.
The Quality field in the Image Attributes group on the Resolutions tab of the Multimedia module may be populated with incorrect data when the `Update Resources` command is used to populate the value.	The correct value is now stored in the Quality field when updated via the `Update Resources` command.
All database generated error messages contain UTF-8 characters where non-ASCII characters are required. If a client has an ISO-8859-1 based system, the error message will not display correctly in the Windows client. The error message is displayed correctly in Unicode (UTF-8) based systems.	All database error messages are now displayed with the correct encoding, regardless of the system character-set used.
The data stored in the Audit Record field on the Summary tab in the Audit Trails module cannot be copied onto the Windows clipboard. If a user selects the data (via `CTRL+A`) and then copies it (via CTRL+C), the data cannot be pasted (via CTRL+V) into another application.	The data stored in the Audit Record field can now be copied onto the Windows clipboard.
The error message Cannot locate http://... resource on server may appear when the Multimedia>Launch Viewer command is invoked. The page is opened correctly if the Launch Viewer button on the Multimedia Toolbar is selected or the image in the Image pane is double clicked.	The error message no longer occurs and the correct page is displayed when the Multimedia>Launch Viewer command is invoked.
If data is entered into the second or subsequent rows of the Notes Summary table on the Notes tab in the Conservation module and the record saved, the data in the second and subsequent records is not saved. Any data entered into the first row is saved correctly.	Data entered into the second and subsequent rows is now saved correctly.
If the Parent field links to the current record and the Parts tab is displayed in the Catalogue module, the Windows client will appear to freeze. The problem is caused by a link referring to itself.	The Parent linking code has been modified to check for records that link to themselves. If a record is found, a suitable message is displayed and an empty Parts tab displayed.
When dittoing into a linked field in a LinkGrid control via the Edit>Ditto>Current Field command, the linked module is invoked and a search conducted using the value in the dittoed field. Since the value is being dittoed, the linked module should not be invoked and the value just added to the grid.	The linked module is no longer invoked when dittoing a value into a link field in a LinkGrid control.
Under certain conditions the server-side Lookup List server (lutserver) may delete values from the Lookup List module when the values are still in use. The entries are only deleted if a given value has more than one punctuation variant (e.g. "Brown, Bill" and "Brown - Bill"). Entries should only be deleted if they are no longer used in any records.	The Lookup List server no longer deletes values that are still in use.
The server-side Lookup List server (lutserver) may delete values from the Lookup List module where a Lookup List value is a subset of a longer Lookup List value (e.g. "Damage" and "Paint Damage"). Entries should only be deleted if they are no longer used in any records.	The Lookup List server no longer deletes values that are still in use.
The Calendar pop-up button is still displayed when its associated field is hidden by permissions. The issue only arises in Query mode where the associated control has had the `dvQuery` permission removed from the Column Access Registry entry.	The Calendar pop-up button is now hidden when its associated field is hidden.
If the Lookup Exact Registry entry is enabled on a field in a hierarchy and a value is selected from the Lookup List in Query mode, the displayed value is enclosed in double quotes. If a search is performed, no matching records will result. The lack of matches is caused by the double quote characters being included in the search.	The double quote characters are removed from the search term when the query is performed for columns that have the Lookup Exact Registry entry enabled.
The Column Access Modifier Registry entry may not be applied correctly when the field whose value is being checked contains a list of values. The issue only arises if there are three or more values in the list.	The Column Access Modifier Registry entry is applied correctly for list fields regardless of the number of entries in the list.
The Add Resource... button on the Multimedia tab in the Multimedia module may become hidden when a user changes to either Medium or Large fonts in the Windows font settings.	The Add Resource... button now displays correctly regardless of the user's Windows font setting.
The error message TexAPI Error: End of file. (Number -18) may occur when the last record in the Multimedia module is deleted while in List View. The error will only occur if the last record had an image associated with it.	The error message no longer occurs when the last record is deleted in List View.
The EMu date and time formats are not applied to values entered into fields created as Admin Task parameters. The current Windows format is used which may cause a mismatch between the value entered and the value expected by the Admin Task handler.	The correct date and time formats are now applied to Admin Task parameters.
Attaching batches of records to the Delete tab in the Operations module via drag and drop from the Catalogue module may be very slow, even for small numbers of records.	The time taken to attach records to the Delete tab has been improved significantly.

EMu 4.2

Release Date: 8 October 2013

Requirements

Windows 2000, XP, 2003, Vista, Windows 7, Windows 8
Texpress 8.3.012 or later
TexAPI 6.0.011 or later
Perl 5.8.8 or later

Issues Resolved

Issue	Resolution
The splitting of date ranges may result in the current century being prepended to the closing value rather than the century of the opening value. For example, 1886-93 would result in 1886 and 2093 as the opening and closing values respectively. In most instances a closing value of 1893 is required.	The closing value of a date range now reflects the century of the opening value, rather than the current century.
The Multimedia and Supplementary_tab fields may not appear in the list of fields available for selection when creating a report. In order to add the fields it is necessary to add Reportable Registry entries for each of the fields.	The Registry entries are no longer required as the Multimedia and Supplementary_tab fields are now shown in the field list (permissions permitting).
The `auditserver` may not complete processing the current record when it is terminated. When it is restarted it may then process the same record again, possibly resulting in two entries in the Audit Trails module.	The `auditserver` now finishes processing the current record before shutting itself down.
Admin Tasks that have specified input types of either number, date or time do not have values entered validated. Hence it is possible to enter a badly formatted number, date or time value that is not detected until the server-side script checks its arguments.	Numeric, date and time values entered as input values in Admin Tasks are now checked when the field containing the value is exited. If the value is not valid, a suitable message is displayed and the value must be amended.
The `emulutsrebuild` server-side command does not load system based Lookup Lists when they are named on the command line. For example, emulutsrebuild -t 'System Yes' does not add the Lookup List entry for the System Yes Lookup List.	System based Lookup List entries are now loaded correctly when named on the command line.
When selecting a file to import into EMu the file selection dialogue box restricts the file extensions that may be chosen. The list of possible files is restricted to those matching `.csv`, .tab, .txt and .xml. In some cases an Import file may not match one of the listed extensions, forcing users to rename files.	The file selection dialogue box has been extended to allow All Files (.) to be selected. The change allows any file to be chosen. EMu parses the first part of the file to determine whether it contains XML or CSV based data.
When copying a large number of rows from a list of matching records onto the Windows clipboard, the operation may take a long time. In particular, if the data contains values from other modules the time taken may be substantial.	The time taken to copy records onto the Windows clipboard has been reduced dramatically where a large number of records is involved.
The Summary Data generated for the Accession Lots module contains only the name of the first person listed as the source of the object(s). In the case where multiple sources have been involved the Summary Data does not reflect this involvement. In this case the value displayed may be misleading.	The Summary Data for the Accession Lots module now lists all parties listed as a source of the object(s).
The file permissions set on the EMu server allow access to server-side files for users registered in the UNIX group `emuadmin`. In general, user emu is the only account that is part of the emuadmin group. If a System Administrator chooses to add another user to the group, the user may be able to view information that is sensitive.	The EMu server-side permissions have been tightened so that only user `emu` may view files containing information that may be sensitive.
If a Catalogue object is attached to an Event where the object is already part of the event and the Exhibition Objects module is used by the Institution, then EMu will display a message indicating that the object is already part of the event. Once the message is acknowledged the same message may be displayed again and again. The only way to exit the messages is to close EMu.	The message indicating that the object is already part of the event is now displayed once only.
The header displayed at the top of each column in List mode may not display the text correctly if the text contains extended characters (that is characters with diacritics).	The header text is now displayed correctly for extended characters.
The data shown in the Shortcut grid for a given record may not display correctly. The issue only arises for users with Unicode based data where the data contains extended (or non-ASCII) characters.	Unicode data is now displayed correctly in the Shortcut grid.
The message box displayed asking for confirmation for a new entry to be added to a Lookup List may not display the new value correctly for Unicode based systems where the value contains extended (or non-ASCII) characters.	The correct text for the new value is now displayed for extended Unicode characters.
When a series of rows in List mode is copied to the Windows clipboard the data copied may not display correctly if pasted into Microsoft Excel. The issue only arises for Arabic characters.	Arabic characters now paste correctly into Microsoft Excel.
When a series of rows in List mode is copied to the Windows clipboard and then pasted into Microsoft Word any diacritic characters will not be displayed correctly. The issue only occurs for non-Unicode based clients. The issue does not occur if the Paste Special... command is used in Microsoft Word.	All diacritic text pasted into Microsoft Word now displays correctly.
The error message Cannot allocate memory may be displayed when copying a large number of rows from List mode onto the Windows clipboard. The issue only occurs where the number of rows is in the tens of thousands.	The error message no longer appears when copying a large number of rows onto the Windows clipboard.
An incorrect hint string is displayed when hovering over the Discard Record speed button. When a series of records is selected the Discard Current hint is displayed, rather than the Discard Selected Records hint.	The correct hint is now displayed when hovering over the Discard Record speed button.
If an object is removed from an event record by simply clearing the Summary Data of the object from the Objects gird, then the associated Exhibition Objects record is not deleted. If the object is deleted by right clicking on the object's Summary Data and selecting Delete..., then the Exhibition Objects record is deleted correctly.	The Exhibition Objects record is now deleted when the Summary Data of the associated record is cleared.
Multimedia records attached to the Exhibition Objects module are not displayed as thumbnails by default. The full version of the image is shown. The Multimedia tool bar can be used to switch to Thumbnail mode.	The Exhibition Objects module now displays multimedia thumbnails by default.
The command to insert the current date (Edit>Date>Current Date) may insert the date for the previous day. The incorrect date, while consistent, will only occur spasmodically.	The correct date is now inserted.
The `lutserver` server-side load may fail with a Not enough space error message even though there is plenty of space available. The error occurs when the load has a large number of updates to process.	The `lutserver` load no longer fails with an Not enough space error message when processing a large numbers of updates.
The Column Access Modifier Registry entry may not be triggered until a record is saved. The issue only arises if the column being monitored for changes is not one of the columns used for tab switching.	The Column Access Modifier Registry entry is always triggered when the column being monitored is exited after being modified.
The error message You cannot Edit no matching records in Column column with value 'value' may be displayed when using the Import tool to import data. The issue only arises for CSV based data where data is inserted into the same module twice. A typical scenario is importing a Bibliography record which in turn accesses another Bibliography record.	The error message is no longer displayed when importing data that accesses the same module twice.
The Bulk update tools provided on the Tools menu do not honour the Column Attach Registry entry. The affected tools are for Relocations, Condition Checks, Re-identification and Revaluation. If a Registry entry has been specified, invoking an attachment to the appropriate module results in the Registry entry being ignored.	The Column Attach Registry entry is now triggered when using attachments in any of the Bulk update tools.
The error message List Index out of bounds(0) may be displayed when importing data into a multi-lingual EMu system. The error only occurs when importing values into a hierarchy where one or more of the levels of the hierarchy is empty.	The error message is no longer displayed when importing data where one or more levels in a hierarchy is empty in a multi-lingual system.
If text is entered into a grid control in Query mode and the Insert Record speed button is selected before exiting the grid, an Access Violation error message may be displayed.	The error message no longer displays when clicking the Insert Record speed button.
If an Admin Task is defined in a multi-lingual system where strings are provided for all languages as part of the Registry entry, then the strings displayed show all languages rather than the current language selected.	The Admin Task now displays strings in the current language selected, rather than displaying all strings.
If a user has defined a different font colour for data when editing or creating a record and a value in a computed field is modified, the record will stay in Edit mode after the save command has been invoked. The issue only arises where a special handler has been installed to handle a computed value (e.g. Currency conversion).	The record no longer remains in Edit mode for computed fields when saved.
The ICS files generated by EMu may not contain the correct format. The ICS files contain a list of notification dates suitable for uploading into calendar applications like Microsoft Outlook, etc.	The ICS files generated now contain the correct format.
The `lutserver` server-side load may create a new Lookup List entry for Unicode based entries that already exist where the entry contains extended (or non-ASCII) characters. The entry created may not contain the correct data.	A new entry is no longer created when the Unicode based Lookup List entry exists, even if it contains extended characters.
The data displayed below the thumbnail image in Contact Sheet mode may appear incorrectly for Unicode based data where extended (or non-ASCII) characters are part of the data.	The correct data is now displayed for Unicode extended characters.
The `lutserver` server-side load may generate an error when checking whether a Lookup List value still exists. The Server error: Can't find "/home/emu/client/data/column" directory. Unable to resolve "column" error message only occurs where the hierarchy contains a virtual column. In this case the Lookup List entry should not check the column.	A Lookup List hierarchy containing a virtual column is no longer checked by the `lutserver` when determining whether an entry is still valid.
An Access Violation error message may be shown when clicking on the After Export tab in the Export Properties dialogue box. The issue only occurs if no After Export scripts have been installed.	The error message no longer appears when clicking on the After Export tab in the Export Properties dialogue box.
If a Lookup List field contains a value consisting of punctuation characters only, then when the record is saved the user will be asked to confirm the insertion of a new Lookup List even if the value is already in the Lookup List.	The confirmation message for Lookup List values which consist of punctuation only is displayed once, rather than each time the value is encountered.
An Access Violation error message may be shown when copying rows from List mode to the Windows clipboard. The message is only displayed if one of the columns copied is a client-side column (DataLocal column).	The error message is no longer displayed when copying rows to the Windows clipboard where one or more of the columns is a client-side column.
If a new value is entered into a Combo Box and the record saved, the value is added to the Lookup List module but it may not be added to the Combo Box drop down list. The next time the list is dropped down, the value may be missing.	New values are now added to the drop down list when the record is saved.
The `emulutsrebuild` server-side program may change the Hidden flag on a Lookup List entry from Y (Yes) to N (No) when rebuilding a Lookup List. The issue occurs only where the default Lookup List permissions for the column do not contain ReadIgnore, WriteIgnore or AutoWriteIgnore.	Lookup List entries with the Hidden flag set to Y (Yes) are no longer changed by the `emulutsrebuild` server-side program.
If a report contains a reverse reference field, under certain circumstances the data associated with the field may not be included in the report. The issue only arises if the data for the field is a single value. Multiple values are reported correctly.	The data for single value reverse reference fields is now reported correctly.
Error messages generated by the EMu server are not displayed correctly if the text contains extended (or non-ASCII) characters. In particular, French and Arabic errors may display incorrectly.	EMu server error message now display the correct text for all languages including text with extended characters.
The Overdue Loans notification reports, generated on a per user basis, may contain an incorrect list of the object on loan and the count of the object on loan. The issue only arises if the Extended Data for an object in the loan contains a closing bracket character.	The correct list of objects and count of objects is now reported in the Overdue Loans notification reports.
The Movements tab in the Locations module is designed to show all objects that have been moved through the current location. Under some circumstances the list of objects displayed may not be complete. The information regarding the movement is complete, however the Summary Data for the object may be missing.	The list of objects is now complete. An upgrade script is provided that forces empty Summary Data values to be populated correctly.
Under certain circumstances the last character in the Extended Data text may not be displayed as bold. The issue only occurs if the data contains more than one line of text.	All of the Extended Data text is now displayed in bold.
When copying data from List mode to the Windows clipboard and pasting it into Microsoft Excel using the Paste Special: CSV command, the pasted values may not appear in Excel.	Data pasted into Microsoft Excel via the Paste Special: CSV command now appears correctly. Due to limitations in Excel, Unicode based data may contain some question mark characters where Excel cannot map the character to its internal character set.
If a field has a Lookup List associated with it and also is an attachment field (e.g. it attaches to the Thesaurus module) and a value is entered into the field, then under certain circumstances the value entered may be cleared rather than force an attachment lookup. The issue only occurs if the value entered is not in the associated Lookup List.	The value is no longer cleared and the attachment lookup is now triggered correctly.
A System Error. Code: 1400. Invalid Window Handle error message may be displayed after a record is saved. The error only occurs if a default value is set on a Combo Box control that is only visible in Display mode (a very rare combination).	The error message is no longer displayed when saving a record.
If a drag and drop operation is used to add records to a grid control where the record has been changed by another user, then the record is refreshed and the drop operation removes the changes made by the previous user. The issue only occurs if the grid on which the drop operation is performed was modified by another user after the record was retrieved.	If a drop operation occurs on a grid that has been modified by another user, a message is displayed and the drop operation is aborted. The change ensures no data is lost.
Some currency based calculations may result in rounding errors. The issue only arises where the currency value is greater than seven digits of precision.	The rounding error no longer occurs where a currency value consists of more than seven digits of precision.
If data is copied from List mode and then pasted into Microsoft Word while keeping the source format, the data is no longer displayed in a table but rather as unformatted text.	If the Keep Source Format option is selected in Microsoft Word, the pasting data will now appear as a table rather than unformatted text.
The `luts` server-side audit handler generates an error when a name is not associated with a hierarchy. The error causes other audit handlers for the current audit record to be skipped. The issue only arises if a hierarchy has not been configured correctly.	An error is no longer generated if a hierarchy is not configured correctly. The hierarchy is skipped and all audit handlers are executed correctly.
An Admin Task may be executed inadvertently by displaying the list of available Admin Tasks and then double clicking anywhere in the Admin Task dialogue box. The issue only arises if a task is selected when the double click is executed.	An Admin Task is only executed if the double click occurs on the task selected, otherwise no action is taken.
If the `emulutsrebuild` server-side command is executed with a Lookup List name supplied as a command line argument and the lookup name matches an existing Lookup List name but the character case is different, then the Lookup List entries for the existing name are deleted.	The Lookup List entries are no longer deleted if the Lookup List name supplied does not match exactly the character case of an existing Lookup List.
When performing an attachment query the Searching dialogue box may display a status of Optimising Search that may never change. The only way to exit the dialogue box is to terminate EMu. The issue only occurs if an open module is displaying a grid that has custom functionality added to it. Normal grids do not exhibit this issue.	The attachment query no longer hangs when a grid containing custom functionality is displayed.
The Mandatory Modifier Registry entry may not be triggered when a dependent value changes in a nested column. The issue only occurs when the value to check is part of a nested column (a column name ending in _nesttab).	The Mandatory Modifier Registry entry is now triggered correctly for nested columns.
Under certain circumstances the value displayed in a query grid for an attachment query (e.g. <# 4 #>) may result is a search for the number of records (in this case 4) rather than the attached records. The issue only occurs if the cursor is placed in the query field after the attachment process is completed.	The attached records are always used as part of the query rather than the number of attached records.
Under certain circumstances the resolution height and width set on the Multimedia tab in the Report Properties dialogue box may not be honoured when the report is generated. The issue only arises if the Multimedia field is the last field listed in a report group.	The resolution height and width settings are honoured when the Multimedia field is the last field listed in a report group.
The Column Access Modifier and Mandatory Modifier Registry entries are not triggered when creating records using the EMu Record Template facility.	The Column Access Modifier and Mandatory Modifier Registry entries are now triggered correctly.
If a multi-page TIFF image is ingested by the Multimedia Repository, then the last page of the document is used to generate the thumbnail image rather than the first page. Since the last page may be a lower resolution image of the first page a blurry thumbnail may be produced.	The first page of a multi-page TIFF document is used to generate the thumbnail and resolution images.
The image types PDF and DNG are not recognised as image formats when producing a report with the Use first image only option enabled. As such, an image is not displayed in the report.	Both PDF and DNG are now recognised as image formats when generating reports.
The error message Can't find "/data/emu/client/data/AssParentObjectRef" directory. Unable to resolve "AssParentObjectRef". may occur when relocating objects using the Internal tab in the Movements module. The error displays when the New Location and Date Moved fields are updated and the movement is saved.	The error message no longer appears when the Movement record is saved.
The Summary tab in the Audit module may not display extended (or non-ASCII) Unicode characters correctly. Data stored as ISO-8859-1 (latin1) will be displayed correctly.	Unicode data is now displayed correctly on the Summary tab in the Audit module.
If a double click occurs on a row in List mode or on a cell in Contact Sheet mode and the mouse cursor is moved away from the row or cell clicked, under certain circumstances the record displayed in Details mode may not be the same as the record on which the click occurred.	The correct record is now displayed in Details mode based on the row or cell on which the double click occurred.

EMu 4.1

Release Date: 14 December 2012

Requirements

Windows 2000, XP, 2003, Vista, Windows 7
Texpress 8.3.010 or later
TexAPI 6.0.009 or later
Perl 5.8.8 or later

Improvements

Issues Resolved

Issue	Resolution
The global replace permission, `daReplace`, is required to perform a number of functions in the EMu client. In particular it is required for: Global Replace Relocate, Revalue, Recondition, Reidentify tools Record Merging A number of requests have been made to create a new permission for record merging, as it is logically a separate activity.	A new permission, `daMerge`, has been added to the set of permissions. The new permission, rather than daReplace, is required to perform record merging.
The Ditto All command allows users to replace completely the contents of an existing record. A request has been made that a new permission be created since all data elements are modified. The privilege will allow System Administrators to restrict who can use the Ditto All command.	A new permission, `daDittoAll`, has been added to the set of permissions. The new permission is required to access the Ditto All command.
If an image is displayed in the Multimedia tab and the user moves to the next record, where the next record contains a video format that is not supported, an error message is displayed indicating that the format is not supported. Once the error message is dismissed, the image of the previous record is still shown.	If a media format is not supported by EMu, the multimedia display on the Multimedia tab is now cleared.
If the multimedia display on the Multimedia tab is showing multiple thumbnails and the view attachments button is selected, all attached multimedia records are displayed in the Multimedia Repository. The selected thumbnail is not the first record displayed, forcing users to move through the multimedia records to locate the required match.	When the view attachments button is selected on the Multimedia tab, all attached records are displayed with the current record set to the thumbnail selected on the Multimedia tab.
The Multimedia Component introduced in EMu 3.2.04 is not supported by the Global Replace facility. It is not possible to add or remove media from the control using a Global Replace command.	Support for the Global Replace command has been added to the Multimedia Component.
The summary data calculated for a citation in the Bibliography module does not include issue information where the citation is from an article.	The article's issue information is now included in the summary data for citation records in the Bibliography module.
If the EMu help files are invoked while the prompt language is set to French (CA), then the English help text is shown rather than the French text. The French text is displayed correctly when the prompt language is set to French.	The French help text is now displayed when help is invoked with the prompt language set to French (CA).
EMu does not provide a way for setting a default value for an attachment field in Query mode. The Set Default Value dialogue box displays the field but does not provide an attachment button to allow records to be selected.	The Set Default Value dialogue box allows records to be attached as default values for attachment fields.
The Column Colour Registry entry does not provide a mechanism for setting the default colour for all controls in a module.	A column name of Default may now be used with the Column Colour Registry entry to set the default colour for all controls in a given module.
The lookup of security settings for the Security tab in property dialogue boxes may be slow when a large number of users are registered on the system.	The lookup speed for security settings has been optimised to provide faster loading of the Security tab in property dialogue boxes.
The text colour used to display records in List View where the record is read only is a light grey colour. The colour makes the text difficult to read against a white background and blue background when the record is selected.	The display of read only records in List View has been modified to use a grey background with black text. The change makes read only records more distinct visually.
The security profile generated for user `emu` does not contain any record level security restrictions (by design). If the emu account is configured to allow multiple groups, the Record Level Security settings will not reflect the group selected. Rather no restrictions will apply. This makes it difficult to test group permissions as user emu.	The security profile generated for user `emu` only provides unrestricted permissions for the first group listed, where multiple groups are supported. In general, the first group listed should be the "super-user" group (usually Admin).
The addition of multiple group support allows a user to be in more than one group, possibly at the same time. The EMu audit trail records do not contain the group of the user who updated, inserted or deleted a record. The user's group is useful for tracing why changes were allowed to a record.	The group of a user who inserts, modifies or deletes a record is now recorded in the audit trail record.
A user may set the format used to display dates via the Date Order Registry entry. The EMu server also has a default date display format. In general these two settings should display the date components (day, month, year) in the same order. If the order is different, then dates entered when searching must be in the server defined order.	Users may now specify a date format with the date components in any order. The order will be used for both data entry and searching.
EMu uses the Windows Registry to try to determine the MIME type for a given file extension. If the MIME type cannot be determined, then the EMu Mime Registry is consulted. An issue arises where a third party application has installed a bad mime type into the Windows Registry. Multimedia records created for that application will contain an invalid mime type value.	The EMu Mime Registry entry has been extended to allow it to override an entry in the Windows Registry.
The log files generated by the various EMu server-side processes may not output record based data correctly where the data is in UTF-8 format. The log files do not affect any records stored in EMu.	EMu server-side processes now log UTF-8 based record data correctly.
The audit trail data generated for loading into the Audit Trail module may exceed the maximum file size when auditing has been disabled for a reasonable period.	The audit trail data is now split up into a number of files where each file is limited to the maximum file size.
If an attachments fails on a RichEdit control, then the original value is restored to the control. If the RichEdit control is then tabbed off, the RichEdit control will try an attach query again. The second lookup is not required as the RichEdit control has been restored to its original value.	When an attachments fails on a RichEdit control and the original value is restored, the second attachment lookup no longer occurs.
When the context menu is shown in List View by right clicking on a record that is not selected currently, the menu may not have the correct menu options enabled. In particular the multimedia options Save and Launch may be disabled when they should be enabled.	The Save and Launch menu options are now enabled correctly.
An error message may be displayed when invoking a batch update tool (e.g. Relocation) while in List Mode with thumbnail images displayed. The error message is displayed before the update commences.	The error message no longer occurs when a batch update takes place in List View with thumbnails displayed.
If an entry is selected from a ComboBox, where the associated column has a form set via the EMu Format Registry setting (e.g. convert to upper case), then the format is not applied to the value selected.	The format setting is now applied for all ComboBox selections where a format has been specified.
The language encoding setting on the EMu server was updated to use "standards" based names. The old utf8 setting was changed to utf-8. The change was not propagated to all areas of the client, causing some messages to be displayed incorrectly.	The utf-8 language encoding is now supported for all messages within the EMu client.
Images created using Olympus cameras cannot be loaded into the Multimedia Repository. The EXIF generated does not conform to the EXIF standard, causing the EMu client to generate large amounts of EXIF data.	The EMu EXIF parser has been enhanced to parse data in images generated by Olympus cameras.
If the value in a ComboBox is used to determine which tabs should be shown and the ComboBox is part of a hierarchy, then an error message may be displayed when a new value forces the tabs to adjust.	The error message no longer occurs when tabs are adjusted due to a change in the ComboBox value.
A series of blank rows may appear at the top of the Resolutions or Documents grids in the Multimedia Repository where an insertion was commenced, an image attached and the insertion then cancelled.	Blank rows no longer appear at the top of the Resolutions or Documents grids in the Multimedia Repository after cancelling an insertion.
The Edit Resource facility does not allow Microsoft Excel documents to be edited. Other Microsoft Office documents can be updated. The problem is due to Excel not registering an Edit mechanism in the Windows Registry.	The Edit Resource facility has been expanded to invoke the View mechanism for a document if an Edit mechanism is not found. The change does not guarantee the document can be modified if the View mechanism is invoked.
The Field Help dialogue box may not be displayed correctly when the option to Save last Size is enabled. The dialogue box shows the help window with a grey area similar in size to the help window next to it.	The correct size for the Field Help dialogue box is now maintained when Save last Size option is enabled.
An Access Violation message may be displayed when closing a crystal report that contains an image (e.g. logo) in the main report and an EMu multimedia image in a sub-report.	The Access Violation message no longer occurs when closing the report viewer.
A Floating point division by zero error message may be displayed when scrolling the HTML version of the Narrative tab in the Narratives module. The error only occurs when Internet Explorer 9 is installed on the user's computer.	The Floating point division by zero error message no longer occurs when scrolling the HTML version of the Narrative tab.
If spell checking is invoked for a language for which a dictionary is not available (e.g. Arabic), then the spell checking configuration dialogue box is displayed. If the location of a dictionary is not selected, the configuration dialogue box cannot be exited.	If a dictionary is not available, the spell checking configuration dialogue box is no longer displayed. A message indicating the dictionary is not available is shown.
The Field Help dialogue box may not display the correct extended information (e.g. Column Name, etc.) the first time it is invoked. The correct information is shown for subsequent invocations.	The correct extended information is now shown the first time the Field Help dialogue box is displayed.
The Intended Audience field in the Events module was not configured on the EMu server to allow a table of values. The EMu client allowed multiple values to be input, however the values were saved as a string of text, rather than as a table of values.	The Intended Audience field has been converted to a table on the EMu server.
An Access Violation error message may be displayed when Copy and Paste is used to set a default value in Query mode via the Set Default Value dialogue box.	The Access Violation error message no longer appears when setting a default value via Copy and Paste.
If the escape key (ESC) is pressed when the Save Changes dialogue box is displayed, then the changes are saved rather than being cancelled.	The escape key now cancels changes made when the Save Changes dialogue box is displayed.
When setting default values for Query mode for CheckBox controls via the Set Default Value dialogue box, the order of the controls in the dialogue box may not be the same as on the tabs.	The order of CheckBox controls in the Set Default Value dialogue box is now the same as on the Query tabs.
When inserting a new record from Query mode, the Status Bar at the bottom of the module form may indicate a number of records are selected. No records should be selected since the insertion started from Query mode.	The Status Bar no longer indicates any records are selected when an insertion is started from Query mode.
If List View is displaying more columns than can be shown on the screen and the screen is scrolled to the right and a row number is selected, then the List View scrolls to the left most column. The scrolling of the columns makes it difficult to compare data in the right most columns as they have scrolled off the screen.	List View no longer scrolls to the left most column when a row is selected.
When a new group is created for a set of record, the group name is not added to the Lookup List of group names until the next day.	The Group Name for newly created groups is now added to the Lookup List when the group is saved.
The Reports Properties dialogue box may display an incorrect Modified time for the report file when daylight savings is in effect. The time displayed is one hour behind the correct time.	The correct Modified time for the report file is now displayed.
The error message Cannot load image resource "ListImg" may be displayed when viewing default values via the Set Default Value dialogue box. The error only occurs when an invalid value is set on a date field.	The error message no longer appears when an incorrect default value is set on a date field.
If the Edit>Clear command is invoked in a grid in Display mode, then the value with focus is cleared in the grid, however EMu does not change to Edit mode and if the record is refreshed the cleared value is re-displayed.	When the Edit>Clear command is invoked in a grid, EMu changes to Edit mode and the value with focus is cleared.
If Shortcuts View is enabled in Query mode in the Parties module, the layout of the Person tab may be incorrect. Some of the prompts for the field may not appear in their correct position.	All prompts now appear in their correct position when Shortcuts View is enabled in Query mode for the Parties module.
The error message TexAPI Error. Cannot allocate memory (Number 100) at offset 0 may occur when the Viewing Attached>Selected Records command is invoked on a large number of selected records (e.g. 150,000).	The error message no longer appears when the Viewing Attached>Selected Records command is invoked on a large number of selected records.
An Access Violation message may be displayed when a new version of ImageMagick is installed on a user's computer and EMu is configured to use the new version. The message is not displayed if the version of ImageMagick distributed with EMu is used.	The error message is no longer displayed if a newer version of ImageMagick is used.
If a language other than All Languages is selected in the Report Properties dialogue box for a multi-lingual system (e.g. English/French), then the Language selection is not saved correctly when the properties are exited.	The Language selected in the Report Properties dialogue box for a multi-lingual system is now saved correctly.
Any Insert Defaults Registry entry for the Exhibition Objects module is not applied when a new record is created implicitly from the Events module.	Any Insert Defaults Registry entry is now applied for all new Exhibition Object records.
The `emusecurity` server-side program may not be run automatically when Security Registry entries are removed. The issue only occurs when a Registry entry is changed from a security based entry to another type of Registry entry.	`emusecurity` is now run automatically when Security Registry entries are changed to another type of Registry entry.
When an image is added to the Multimedia Repository, the modified time on the original image may be changed. The original image itself is not changed, just the modified time.	The modified time is no longer changed on the original image when added to the Multimedia Repository.
If a macron character is entered into a RichEdit control, then all text stored after the macron character will be displayed in a different font. The issue only occurs when the text is viewed in Display mode.	Text after a macron character is now displayed in the correct font.
Macron based characters may not be displayed correctly in the HTML tabs in EMu (e.g. Narratives tab in Narratives module). All other characters are displayed correctly.	Macron characters are now displayed correctly in EMu's HTML tabs.
In some instances the Find a Field dialogue box may list some prompts that do not contain data in the Catalogue module. If one of the prompts is selected, the prompt displayed by the data component is always empty.	Prompts for controls that do not contain data in the Catalogue module are no longer shown in the Find a Field dialogue box.
The list of fields available for reporting may contain some columns that cannot be viewed in Details View. Since the column cannot be displayed, values cannot be entered so the columns should not be selectable for reporting.	Only columns that are displayed can be selected for reporting.
Under certain circumstances it is possible to save a record where a hierarchy of values does not exist in the Lookup List module, without being asked to confirm the new combination. The issue only arises if the new combination matches an existing entry except the new combination has some empty values.	The user is now prompted to confirm the new hierarchy of values.
An Access Violation error message may be displayed when switching to Page View if the XSLT report used to generate the view does not exist on the EMu server.	A suitable error message is now displayed if the XSLT report does not exist on the EMu server.
The EMu Import facility does not honour the Column Access Modifier Registry entry settings. Hence users may not be able to update values for which they have been granted dynamic access.	The Import facility now honours the Column Access Modifier Registry entry.
A Grid index out of range error message may be displayed when the Page Down key is pressed to try and move past the last page of records.	The error message no longer appears when trying to "Page Down" past the last page.
The keyboard shortcut to insert the current date (`CTRL+;`) does not work on a French keyboard.	The keyboard shortcut for the current date now works correctly for French keyboards.
When switching prompt languages from English to French, dates displayed with the months as text did not change to use the text of the new prompt language. The issue only occurs if the language is changed in the current session.	The text values for months in dates are now changed correctly when the prompt language is changed.
If a Lookup List is displayed on a grid control which in turn is controlled via another grid control (a so called Nested Form construct), then the list may not be restricted to the set of values valid for the existing hierarchy.	The correct list of values is now displayed for hierarchies represented by two grids linked together.
When attaching a Taxonomy parent record to a new record, the Family Number, Genus Number, Species and Subspecies fields do not display their values from the parent record. Swapping to another tab and back causes the values to be displayed.	The Family Number, Genus Number, Species and Subspecies fields now display the parent values as soon as the attachment is complete.
If the Down arrow key is pressed in an empty ComboBox control, the list of values may not scroll through the control. The issue only arises if a value is not selected in the ComboBox control.	The Down arrow key now scrolls though the list of values in a ComboBox control when a value is not selected initially.